Systems and methods for removing point of sale processing from pci scope

ABSTRACT

The methods and systems described herein provide for processing payments via a mobile device at a retail location while relying solely on non-PCI Scope information at the retail location. A payment processing transaction may be initiated at a point of sale at a retail location, and a unique identifier provided by a mobile device may be used as payment information to facilitate the processing of a payment transaction. Authorizations of payment processing transactions are made by a remotely located server based, at least in part, on the unique identifier provided by the mobile device.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/861,869 filed on Sep. 22, 2015, which is a continuation of U.S.application Ser. No. 13/302,045 filed on Nov. 22, 2011. Each of theseapplications is incorporated herein by reference in its entirety.

BACKGROUND

Retailers, such as grocery stores, department stores, and restaurants,process thousands of credit card, debit card, and gift card transactionsper day. One requirement for doing so is compliance with the PaymentCard Industry Data Security Standard, also known as “PCI DSS,” or simply“PCI”. Ensuring that a retailer's payment processing computers, cashregisters, back office servers, and credit card terminals comply withPCI can be time consuming and expensive. Various technical andnon-technical standards and practices must be abided by for PCIcompliance, and the retail location can be subject to frequentassessments and auditing.

Components of a retail system which handle secure payment information,also known as “cardholder data”, must meet the requirements of PCI.These components may be referred to as “within PCI Scope”. Componentsthat do not handle secure payment information may be referred to as“outside PCI scope”. Similarly, information whose processing andtransmission would mandate that the hardware and software infrastructurehandling said information fall within PCI scope may be referred to a“PCI scope information”, whereas information whose processing would notsubject the underlying infrastructure to PCI scope may be referred to as“non-PCI scope information”.

Typically, a retail location which has more than one point of salelocation, such as numerous check-out lanes at a department store orgrocery store, generally has the following payment processinginfrastructure: a cash register which provides a user the ability to sumthe total amount of purchases for the transaction; a credit cardterminal for inputting payment card information; and a back officeserver that manages the various cash registers and credit cardterminals, and which is relied upon for the processing of paymenttransactions.

Restaurants may also similarly have multiple point of sale locations foreffectuating the processing of payment transactions. Rather than acheck-out lane, a waiter may take your payment card to a kiosk forprocessing the transaction. Said kiosks may similarly have a computerthat may act as an electronic cash register and a credit card terminal.Sometimes, rather than a kiosk, a restaurant may have mobile wirelesscredit card terminals which a user may use to process a paymenttransaction.

In standard setups, the entirety of the retail location's payment systeminfrastructure must be within PCI scope, including the cash registers,the credit card terminals, and the back office computer systems. Often,the back office computer systems track transaction processing and areresponsible for communicating with a remote authorization service inorder to authorize the transaction. Since in traditional setups all ofthese items fall within PCI Scope, a retailer can be expected to spendsubstantial amounts of resources, time, and money in assuring PCIcompliance across the entire system.

SUMMARY

Applicant has appreciated that available technology for processingpayment transactions requires that retailers spend valuable resourcesand time on PCI compliance. Traditional systems and methods forprocessing payment transactions focus on securing and monitoring everyaspect of a retailer's payment processing infrastructure, from thecredit card terminals, to the cash registers, to the back officeservers, and the network itself. Applicant has further appreciated thatno available technology exists for transitioning existing multiple lane(“multi-lane”) payment processing infrastructure into setups whichremove the majority of the payment processing infrastructure from PCIscope; thereby substantially reducing costs and overhead on PCIcompliance. Applicant has discovered that by effectively isolating acredit card terminal at a retail location, and substantially managingpayment processing by a server at a location remote to a retail locationin direct contact with a credit card terminal, substantial reductions inPCI compliance costs may be obtained.

Applicant has further appreciated that sensitive data, includinginformation typically stored on payment cards, should be securelytransmitted, stored, and processed.

In accordance with one embodiment of the invention, a back office serverat a retail location may be in communication with a plurality of pointof sale lanes and credit card terminals to effectuate the processing ofpayment transactions. The back office server may also communicate with aremotely located customer relationship management server to facilitatethe use of customer loyalty programs, analytics, and receipt storage,tracking, and access. The plurality of credit card terminals are indirect communication with a remotely located payment processing server.The connection allowing communication between the credit card terminalsand the back office server may be limited to a single port, such as asingle isolated TCP/IP or UDP port. The remotely located paymentprocessing server is responsible for communicating with an authorizationserver which may authorize or decline a particular payment processingtransaction. The credit card terminal may communicate with the paymentprocessing server over the public Internet, over a Virtual PrivateNetwork, or any form of wide area network. Communications may beadditionally secured by firewalls disposed at either the retail locationor remote location, or both. Additional security mechanisms, such ashardware monitoring devices which assure and prevent network tampering,may also be disposed at either the retail location, remote location, orboth.

In some embodiments of the invention, a back office server at a retaillocation may be in communication with a single point of sale lane and asingle credit card terminal to effectuate the processing of paymenttransactions. The single credit card terminal may be in directcommunication with a remotely located payment processing server.

In accordance with a further embodiment of the invention, a method forprocessing payments is provided, the method comprising: receiving arequest to process a payment transaction; determining that the requestis associated with one of a plurality of credit card terminals at aretail location; receiving, by the determined credit card terminal,secure payment information; sending, by the determined credit cardterminal, secure payment information to a remotely located server forauthorization; and receiving, by the credit card terminal, anauthorization from a remotely located server.

In some embodiments, a method for processing payments is provided, themethod comprising: receiving a request to process a payment transaction;determining that the request is associated with a credit card terminalat a retail location; receiving, by the determined credit card terminal,secure payment information; sending, by the determined credit cardterminal, secure payment information to a remotely located server forauthorization; and receiving, by the credit card terminal, anauthorization from a remotely located server. In accordance with afurther embodiment of the invention, a method for processing paymenttransactions wherein the request to process a payment is received from asingle point of sale lane at a retail location is provided. Inaccordance with a further embodiment of the invention, a method forprocessing payment transactions wherein the request to process a paymentis received from a single electronic cash register at a retail locationis provided.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions further comprising the step of sending arequest to a determined credit card terminal to initiate receipt ofsecure payment information is provided. In accordance with a furtherembodiment of the invention, a method for processing paymenttransactions wherein the request to process a payment is received fromone of a plurality of point of sale lanes at a retail location isprovided. In accordance with a further embodiment of the invention, amethod for processing payment transactions wherein the request toprocess a payment is received from one of a plurality of electronic cashregisters at a retail location is provided.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions further comprising the additional stepsof: determining that one of a plurality of point of sale lanes at aretail location is associated with an authorization; and sending theauthorization to the determined point of sale lane is provided. Inaccordance with a further embodiment of the invention, a method forprocessing payment transactions comprising the additional steps of:determining that one of a plurality of electronic cash registers at aretail location is associated with the authorization; and sending theauthorization to the determined electronic cash register is provided.

In some embodiments of the invention, a method for processing paymenttransactions further comprising the additional steps of: determiningthat a point of sale lane at a retail location is associated with anauthorization; and sending the authorization to the determined point ofsale lane is provided. In accordance with a further embodiment of theinvention, a method for processing payment transactions furthercomprising the additional steps of determining that an electronic cashregister at a retail location is associated with the authorization; andsending the authorization to the determined electronic cash register isprovided.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions wherein secure payment information issent to a remotely located server through a firewall is provided.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions wherein determining a credit cardterminal associated with a request is based, at least in part, on aticket associated with the request is provided. In accordance with afurther embodiment of the invention, a method for processing paymenttransactions wherein determining a credit card terminal associated witha request is based, at least in part, on a table listing theassociations of credit card terminals.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions further comprising storing non-PCI scopepayment transaction information in a database. In some embodiments, suchnon-PCI scope payment transaction information may be stored at theretail location. In some embodiments, such non-PCI scope paymenttransaction information may be stored at a remote location. In someembodiments, such non-PCI scope payment transaction information may bestored at both a retail location or remote location.

In accordance with a further embodiment of the invention, a method forprocessing payments is provided. A request to process a paymenttransaction is received by a back office server. The back office serverdetermines that the request is associated with one of a plurality ofcredit card terminals at a retail location. The back office server sendsa request to the determined credit card terminal to initiate the receiptof secure payment information to be applied to the requestedtransaction. The determined credit card terminal receives the requestand initiates the receipt of secure payment information. The securepayment information is received by the credit card terminal, and maycomprise credit card information, debit card information, associatepersonal identification number (PIN) information, gift card information,or loyalty program information. The credit card terminal sends thesecure payment information to a remotely located payment processingserver. The payment processing server manages the request and contacts aremotely located authorization server to authorize the payment. Theremotely located payment processing server receives an authorization forthe payment transaction, and sends the authorization to the credit cardterminal. The credit card terminal receives the authorization from theremotely located server. The credit card terminal communicates theauthorization, without sending secure payment information, to the backoffice server. The back office server determines that the authorizationis associated with one of a plurality of point of sale lanes at theretail location. The back office server then communicates theauthorization to one of a plurality of point of sale lanes at the retaillocation.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions wherein a back office server operates inlistening mode awaiting a request to process a payment transactions isprovided.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions further comprising the additional stepsof: determining, based at least in part on payment information, that acustomer belongs to a loyalty program; and applying loyalty programinformation to a requested transaction. The step of determining that acustomer belongs to a loyalty program may be performed at a remotelylocated server, or at a back office server at a retail location.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions further comprises determining, based atleast in part on payment information, a token for a customer. The tokenmay be used as a universal identifier for a customer which does notcontain PCI scope information.

In accordance with a further embodiment of the invention, a method forprocessing payment transactions further comprises storing receiptinformation for the payment transaction. Receipt information may bestored at a remote location, or at a back office server.

In accordance with a further embodiment of the invention, a system forprocessing payment transactions is provided, the system comprising: atleast one processing unit communicatively coupled to a memory unitcapable of storing processor-executable instructions, wherein uponexecution of the processor-executable instructions, the at least oneprocessing unit: receives a request to process a payment transaction,and determines that the request is associated with one of a plurality ofcredit card terminals at a retail location; and a determined credit cardterminal comprising at least one processing unit communicatively coupledto a memory unit capable of storing processor-executable instructions,wherein upon execution of the processor executable instructions, the atleast one processing unit: receives secure payment information, sendssecure payment information to a remotely located server forauthorization, and receives an authorization from a remotely locatedserver.

In accordance with a further embodiment of the invention, at least onenon-transitory compute readable medium is provided, encoded with aplurality of instructions that, when executed, perform a method forprocessing payment transactions. The method may comprise: receiving arequest to process a payment transaction; determining that the requestis associated with one of a plurality of credit card terminals at aretail location; receiving, by the determined credit card terminal,secure payment information; sending, by the determined credit cardterminal, secure payment information to a remotely located server forauthorization; and receiving, by the credit card terminal, anauthorization from a remotely located server.

In accordance with some embodiments of the invention, any embodimentwhich may involve a plurality of credit card terminals, point of salelanes, or electronic cash registers may alternatively involve a singlecredit card terminal, point of sale lane, or electronic cash register.In some embodiments, there may be a single credit card terminal but aplurality of point of sale lanes or electronic cash registers. In someembodiments, there may be a single point of sale lane but a plurality ofcredit card terminals and electronic cash registers. In someembodiments, there may be a single electronic cash register but aplurality of credit card terminals and point of sale lanes.

BRIEF DESCRIPTION OF THE FIGURES

The foregoing and other objects, aspects, features, and advantages ofthe disclosure will become more apparent and better understood byreferring to the following description taken in conjunction with theaccompanying drawings, in which:

FIG. 1 is a block diagram of a system for processing paymenttransactions.

FIG. 2 is a block diagram of an exemplary embodiment of a system forexecuting computer executable instructions performed by processingarrangement and/or a computing arrangement, according to one embodimentof the present disclosure.

FIG. 3 is a block diagram of a system for processing paymenttransactions.

FIG. 4 is a block diagram demonstrating the flow of a method forprocessing payment transactions.

FIGS. 5A is a flow diagram of a method for processing paymenttransactions.

FIG. 5B is a flow diagram of a method for processing paymenttransactions.

FIG. 6A-B are flow diagrams of methods for processing paymenttransactions.

FIG. 7A-B are block diagrams of systems for managing clientrelationships in conjunction with systems for processing paymenttransactions.

FIG. 8 is a flow diagram of a method for managing a loyalty program inconjunction with a method for processing payment transactions.

FIG. 9 is a flow diagram of a method for utilizing tokens to managecustomer relationships in conjunction with a method for processingpayment transactions.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof In the drawings, similarsymbols typically identify similar components, unless context dictatesotherwise. The illustrative embodiments described in the detaileddescription, drawings, and claims are not meant to be limiting. Otherembodiments may be utilized, and other changes may be made, withoutdeparting from the spirit or scope of the subject matter presented here.It will be readily understood that the aspects of the presentdisclosure, as generally described herein and illustrated in thefigures, can be arranged, substituted, combined, and designed in a widevariety of different configurations, all of which are explicitlycontemplated and made part of this disclosure.

In reference now to FIG. 1, a system for processing payment transactionsis shown. Point of sale lanes 1, 2, and 3 are in communication with backoffice server 30. Point of sale lanes may be comprised of any form andcombination of point of sale hardware and software, including electroniccash registers, checkout terminals, checkout kiosks, computers, wirelesscheckout terminals, restaurant ordering kiosks, customized desktopcomputers, laptops, wireless devices, tablet PCs, smart phones, or anyother computing device capable of assisting with payment processing at aretail location. A point of sale lane may be a check-out lane or counterat a department store, grocery store, or other form of retail shoppinglocations, or it may be a kiosk at a restaurant or counter at a foodservice retail location, or any other location where a user effectuatesthe processing of a payment transaction. Back office server 30 may be asingle server, a plurality of servers, a server farm, or an allocationof computing services provided by a cloud based provider of computerservices. In some embodiments, server 30 may be a plurality of serversoperated by a plurality of different parties, entities, and serviceproviders. The back office server 30 may be located at the retaillocation or at a remote location.

In some embodiments, point of sale lanes may comprise electronic cashregisters 11, 12, and 13, which are in communication with the backoffice server 30. Electronic cash registers 11, 12 and 13, may be anyform of computing device capable of assisting a user in effectuating theprocessing of a payment transaction. Electronic cash registers may beany one of or combination of point of sale hardware and software,computerized cash register, checkout terminals, checkout kiosks,computers, wireless checkout terminals, wireless computers, restaurantordering kiosk computers, checkout kiosk computers, payment processingkiosk computers, customized desktop computers, laptops, wirelessdevices, tablet PCs, smart phones, iPhones or iPads as provided by theApple Corporation, or any other computing device capable of assisting auser with payment processing at a retail location. In some embodiments,communications between electronic cash registers 11, 12, and 13 andserver 30 are encrypted. In some embodiments, communications betweenelectronic cash registers 11, 12, and 13 and server 30 are encryptedusing public-private key encryption. In some embodiments, communicationsbetween electronic cash registers 11, 12, and 13 and server 30 areencrypted using shared secret key encryption. In some embodiments,communications between electronic cash registers 11, 12, and 13 andserver 30 are encrypted using Secure Socket Layer (SSL) or TransportLayer Security (TLS) protocols. In some embodiments, communicationsbetween electronic cash registers 11, 12, and 13 and server 30 areencrypted using a proprietary encryption scheme. In some embodiments,communications between electronic cash registers 11, 12, and 13 andserver 30 may occur, at least in part, wirelessly.

The back office server 30 is in communication with credit card terminals21, 22 and 23 which are located at the point of sale lanes. In someembodiments, the communication between credit card terminals 21,22, and23 and server 30 may be limited to a single isolated port forcommunication of non-PCI scope information. In some embodiments thesingle isolated port may be a TCP/IP or UDP port. In some embodiments,communications between credit card terminals 21, 22, and 23 and server30 are encrypted. In some embodiments, communications between creditcard terminals 21, 22 and 23 and server 30 are encrypted usingpublic-private key encryption. In some embodiments, communicationsbetween credit card terminals 21, 22 and 23 and server 30 are encryptedusing shared secret key encryption. In some embodiments, communicationsbetween credit card terminals 21, 22 and 23 and server 30 are encryptedusing Secure Socket Layer (SSL) or Transport Layer Security (TLS)protocols. In some embodiments, communications between credit cardterminals 21, 22 and 23 and server 30 are encrypted using a proprietaryencryption scheme. In some embodiments, communications between creditcard terminals 21, 22 and 23 and server 30 may occur, at least in part,wirelessly.

In some embodiments, communications between credit card terminals 21, 22and 23 and server 30 may be made utilizing dial-up communications, theInternet, TCP/IP, UDP, General packet radio service (GPRS)communications, cellular communications, WiFi, wireless communicationsutilizing the IEEE 802.11 standards, other forms of wirelesscommunications, ethernet, or any other form of communications protocol,channel, or standard.

The credit card terminals 21, 22, and 23 are also in communication witha remotely located payment processing server 50. Server 50 may be asingle server, a plurality of servers, a server farm, or an allocationof computing services provided by a cloud based provider of computerservices. In some embodiments, server 50 may be a plurality of serversoperated by a plurality of different parties, entities, and serviceproviders. In some embodiments, the communication between credit cardterminals 21, 22, and 23 and remotely located payment processing server50 goes through one or both of firewalls 60 and 65. In some embodiments,the communication between credit card terminals 21, 22, 23 and remoteserver 50 may be additionally monitored by other software or hardwarebased network monitoring tools. In some embodiments, such networkmonitoring tools may assure that communications between the credit cardterminals and server 50 are not tampered with. In some embodiments,communications between credit card terminals 21, 22, and 23 and server50 are encrypted. In some embodiments, communications between creditcard terminals 21, 22 and 23 and server 50 are encrypted usingpublic-private key encryption. In some embodiments, communicationsbetween credit card terminals 21, 22 and 23 and server 50 are encryptedusing shared secret key encryption. In some embodiments, communicationsbetween credit card terminals 21, 22 and 23 and server 50 are encryptedusing Secure Socket Layer (SSL) or Transport Layer Security (TLS)protocols. In some embodiments, communications between credit cardterminals 21, 22 and 23 and server 50 are encrypted using a proprietaryencryption scheme.

In some embodiments, communications between credit card terminals 21,22, and 23 and remotely located payment processing server 50 may be madeutilizing dial-up communications, the Internet, TCP/IP, UDP, Generalpacket radio service (GPRS) communications, cellular communications,WiFi, wireless communications utilizing the IEEE 802.11 standards, otherforms of wireless communications, ethernet, or any other form ofcommunications protocol, channel, or standard.

In some embodiments, credit card terminals (CCT) 21, 22 or 23 may beterminals that allow customers to swipe or otherwise input credit cardinformation with which to effectuate a payment transaction. In someembodiments, CCTs 21, 22, or 23 may be terminals that allow customers toinput any form of payment information that is not credit cardinformation. In some embodiments, CCTs 21, 22, or 23 may be terminalsthat allow customers to input gift card information, bank accountinformation, or debit card information. In some embodiments, CCTs 21,22, or 23 may be terminals that allow customers to input paymentinformation from an online payment service provider such as PayPal. Insome embodiments, CCTs 21, 22, or 23 may be terminals that allowcustomers to input payment information from a rewards program. Forexample, a user may input rewards program information and use points orcredits to effectuate the payment transaction.

In some embodiments, CCTs 21, 22, or 23 may be terminals that allowcustomers to input information wirelessly. In some embodiments, CCTs 21,22, or 23 may be terminals that allow customers to input informationthrough a Radio-Frequency Identification (RFID) device or chip. In someembodiments CCTs 21, 22, or 23 may be terminals that allow customers toinput information through a touch pad or key pad. In some embodiments,CCTs 21, 22, or 23 may be terminals that allow customers to inputinformation by swiping a card with a magnetic strip. In someembodiments, CCTs 21, 22, or 23 may be terminals that allow customers toinput information by entering in a unique identifier or password.

In some embodiment, CCTs 21, 22, or 23 may be terminals that allowcustomers to input payment information via their cell phones or othermobile device.

In some embodiments, server 50 is in communication with authorizationserver 70. Server 70 may be a single server, a plurality of servers, aserver farm, or an allocation of computing services provided by a cloudbased provider of computer services. In some embodiments, server 70 maybe a plurality of servers operated by a plurality of different parties,entities, and service providers. In some embodiments, communicationsbetween server 50 and server 70 are encrypted. In some embodiments,communications between server 50 and server 70 are encrypted usingpublic-private key encryption. In some embodiments, communicationsbetween server 50 and server 70 are encrypted using shared secret keyencryption. In some embodiments, communications between server 50 andserver 70 are encrypted using Secure Socket Layer (SSL) or TransportLayer Security (TLS) protocols. In some embodiments, communicationsbetween server 50 and server 70 are encrypted using a proprietaryencryption scheme. In some embodiments, communications between server 50and server 70 may occur, at least in part, wirelessly.

In some embodiments, communications between credit card terminals 21, 22and 23 and remotely located server 50 occur across the public Internet.In some embodiments, communications between credit card terminals 21, 22and 23 and remotely located server 50 occur across a virtual privatenetwork (VPN). In some embodiments, communication between credit cardterminals 21, 22 and 23 and remotely located server 50 occur across anyform of wide area network. In some embodiments, communications betweencredit card terminals 21, 22 and 23 and remotely located server 50 occuracross a private network. In some embodiments, communications betweencredit card terminals 21, 22 and 23 and remotely located server 50 mayoccur, at least in part, wirelessly.

In some embodiments, back office server 30 may be in communication withremotely located payment processing server 50. In some embodiments, thecommunication between server 30 and remotely located payment processingserver 50 goes through one or both of firewalls 60 and 65. In someembodiments, communications between server 30 and server 50 areencrypted. In some embodiments, communications between server 30 andserver 50 are encrypted using public-private key encryption. In someembodiments, communications between server 30 and server 50 areencrypted using shared secret key encryption. In some embodiments,communications between server 30 and server 50 are encrypted usingSecure Socket Layer (SSL) or Transport Layer Security (TLS) protocols.In some embodiments, communications between server 30 and server 50 areencrypted using a proprietary encryption scheme.

In some embodiments, server 30, 50 and 70 may be in communication withadditional storage devices or databases.

In reference now to FIG. 2, a block diagram of an exemplary embodimentof a system capable of implementing the present disclosure is shown. Forexample, an exemplary procedure in accordance with the presentdisclosure can be performed by a processing arrangement 110 and/or acomputing arrangement 110. Such processing/computing arrangement 110 canbe, e.g., entirely or a part of, or include, but not be limited to, acomputer/processor that can include, e.g., one or more microprocessors,and use instructions stored on a computer-accessible medium (e.g., RAM,ROM, hard drive, or other storage device).

As shown in FIG. 2 a computer-accessible medium 120 (e.g., as describedherein, a storage device such as a hard disk, floppy disk, memory stick,CD-ROM, RAM, ROM, etc., or a collection thereof) can be provided (e.g.,in communication with the processing arrangement 110). Thecomputer-accessible medium 120 may be a non-transitorycomputer-accessible medium. The computer-accessible medium 120 cancontain executable instructions 130 thereon. In addition oralternatively, a storage arrangement 140 can be provided separately fromthe computer-accessible medium 120, which can provide the instructionsto the processing arrangement 110 so as to configure the processingarrangement to execute certain exemplary procedures, processes andmethods, as described herein, for example.

In reference now to FIG. 3, back office server 30 is comprised of a backoffice manager 32 and a credit card terminal (CCT) manager 34. The backoffice manager 32 may be any computing processor or portion thereofprogrammed to perform the functions of a back office manager. The CCTmanager 34 may be any computing processor or portion thereof programmedto perform the functions of a CCT manager. In some embodiments, the backoffice manager 32 and CCT manager 34 may comprise a single joint backoffice manager and CCT manager. In some embodiments, the functions ofthe CCT manager 34 may be performed by the back office manager 32. Insome embodiments, the CCT manager 34 may perform the functions of theback office manager. The back office manager may be in communicationwith electronic cash registers (ECR) 11, 12, and 13. The back officemanager may be in communication with a payment processing server 51 onremote server 50. The payment processing service 51 may be any computingprocessor or portion thereof programmed to perform the functions ofpayment processing service. The payment processing service 51 maycomprise of a payment gateway. The payment processing service 51 may bea payment gateway.

In some embodiments, the CCT manager 34 is in communication with theback office manager 32, and vice-versa. The CCT manager is further incommunication with CCTs 21, 22, and 23. CCTs 21, 22, and 23 are incommunication with a payment processing service 51 on remote server 50.In some embodiments, communications between payment CCTs 21, 22, and 23and payment processing service 51 are routed through one or both offirewalls 60 and 65.

In some embodiments, payment processing service 51 is in communicationwith authorization service 71 on server 70. The authorization service 51may be any computing processor or portion thereof programmed to performthe functions of the authorization service. Authorization service 71 maybe comprised of a payment gateway. Authorization service 71 may be apayment gateway. In some embodiments, payment processing service 51 andauthorization service 71 may be a single service.

In any embodiment, communications between various components of thepayment processing system may be made utilizing either one or aplurality of: dial-up communications, the Internet, TCP/IP, UDP, Generalpacket radio service (GPRS) communications, cellular communications,WiFi, wireless communications utilizing the IEEE 802.11 standards, otherforms of wireless communications, ethernet, a packet-switched network,or any other form of communications protocol, channel, or standard.

In reference now to FIG. 4, a flow diagram for processing a paymenttransaction in the context of the present disclosure is shown. Backoffice manager 32 receives 401 a request to process a paymenttransaction from ECR 11. The back office manager 32 may validate andcheck the request to determine whether the request is consistent withpayment processing requirements, and transmits the request to CCTmanager 34. CCT manager 34 receives 402 the request from back officemanager 32. CCT manager 34 may determine that CCT 21 is associated withthe request for processing a payment transaction. CCT manager 34 maysend 403 a request to CCT 21 to initiate the receipt of secure paymentinformation. CCT 21 may receive secure payment information from a user,comprising credit card information, debit card information, PersonalIdentification Number (PIN) information, gift card information, orloyalty program information. CCT 21 sends 404 a request to paymentprocessing service 51 to authorize the payment transaction. Paymentprocessing service 51 receives the request to authorize the transaction,and sends 405 a request to authorization service 71 to authorize thetransaction. Payment processing service 51 receives 406 an authorizationfor the payment transaction from authorization service 71. Anauthorization may be any form of computer readable indicator that thepayment transaction has been authorized or approved by an authorizationservice. CCT 21 receives 407 an authorization from payment processingservice 51 and sends an authorization to CCT Manager 34 which does notinclude PCI scope information. CCT Manager 34 receives 408 anauthorization from CCT 21, which does not include PCI scope information.The CCT manager sends an authorization to back office manager 32. Backoffice manager 32 receives 409 an authorization from CCT Manager 34.Back office manager 32 sends 410 an authorization for the paymenttransaction to ECR 11.

In some embodiments, back office manager 32 may operate in listeningmode, whereby it periodically determines whether a request to process apayment transaction has been received, or whether an authorization orother message has been received. In some embodiments, back office server30 may operate entirely in listening mode, whereby it periodicallydetermines whether a request, authorization, message, or signal has beenreceived. In some embodiments, at least one module or process running onback office server 30 may operate in listening mode while other modulesor processes do not operate in listening mode. In some embodiments, CCTManager 34 may operate in listening mode, whereby it periodicallydetermines whether a request to process a payment transaction has beenreceived, or whether an authorization or other message has beenreceived. In some embodiments CCT 21 may operate in listening mode,whereby it periodically determines whether a request to process apayment transaction has been received, or whether an authorization orother message has been received. In some embodiments ECR 11 may operatein listening mode, whereby it periodically determines whether a requestto process a payment transaction has been received, or whether anauthorization or other message has been received. In some embodiments,the periodicity with which a device, module, or process operates inlistening mode may be so short so as to allow an action to be taken inresponse to receiving a request, authorization, or message nearlyinstantaneously.

In some embodiments, an authorization may be a secure packet ofinformation indicating that the payment has been authorized. In someembodiments, an authorization may be an unsecure packet of informationindicating that the payment has been authorized. In some embodiments, anauthorization may be an address in memory that indicated that a paymenthas been authorized. In some embodiments, an authorization may be anelectronic message that indicated that a payment has been authorized. Insome embodiments, and authorization may be a request that the creditcard terminal complete the payment processing transaction. In someembodiments, an authorization may change format between AuthorizationService 71, Payment Processing Service 51, Firewall 65, Firewall 60, CCT21, CCT Manager 34, Back Office Manager 32, and ECR 11. For example, anauthorization received by Payment Processing Service 51 may be a requestby Authorization Service 71 for Payment Processing Service 51 toeffectuate the processing of the payment transaction. In turn, PaymentProcessing Service 51 may communicate the authorization to CCT 21 in theform of a request for CCT 21 to effectuate the processing of a paymenttransaction. In turn, CCT 21 may communicate an authorization to CCTManager 34 in the form of a message to CCT Manager 34 informing CCTManager 34 that the transaction has been authorized. In turn, CCTManager 34 may communicate an authorization to Back Office Manager 32 inthe form of a request to Back Office Manager 32 to effectuate theprocessing of a payment transaction. In turn, Back Office Manager 32 maycommunicate an authorization to ECR 11 in the form of a request to ECR11 to effectuate the processing of a payment transaction, such as arequest to print out a receipt for a customer. In an alternativeembodiment, an authorization may be a single packet of data, file, ormessage which is sent from Authorization Service 71, and forwarded toPayment Processing Service 51, then forwarded to CCT 21, then forwardedto CCT Manager 34, then forwarded to Back Office Manager 32, andforwarded to ECR 11.

In some embodiments, an authorization may be communicated across adifferent communications link than that on which a request forauthorization is communicated.

In reference now to FIG. 5A, a flow diagram for a method for processingpayment transactions is depicted. At a point of sale lane, a userrequests 501 processing of a payment transaction. Further at the pointof sale, a request is sent 503 to the back office server 30 toeffectuate the processing of the payment transaction. Back office server30 receives 505 a request to process a payment transaction. Back officeserver 30 determines 507 which of a plurality of CCTs at a retaillocation is associated with the request. Back office server 30 sends 509a request to the determined CCT to effectuate payment processing. Thedetermined CCT 21 receives 511 the request to effectuate paymentprocessing. The determined CCT 21 prompts 513 a user to enter paymentinformation. Payment information may be comprised of credit cardinformation, debit card information, PIN information, gift cardinformation, or loyalty program information. The determined CCT 21receives 515 secure user payment information. The determined CCT sends517 secure payment information to remotely located payment processingservice 51 along with a request to authorize the payment transaction.Remote payment processing service 51 receives 519 the paymentinformation and request for authorizing the payment transaction.

In reference now to FIG. 5B, a flow diagram for a method for processingpayment transactions is depicted. Payment processing service 51 receives519 the payment information and request for authorizing the paymenttransaction. Payment processing service 51 verifies 521 the request.Payment processing service 51 sends 523 a request for authorization ofthe payment transaction to authorization service 71 for approval.Payment processing service 51 receives 525 an approval or authorizationfor the payment transaction from the authorization service 71. Paymentprocessing service 51 sends 527 an approval or authorization for thepayment transaction to the determined CCT 21. The determined CCT 21receives 529 an approval or authorization for the payment transaction.The determined CCT 21 sends 531 an approval or authorization to backoffice server 30 without PCI scope information. Back office server 30receives 533 an approval or authorization for the payment transactionwithout PCI scope information. Back office server 30 determines 535 thatone of a plurality of point of sale lanes is associated with theapproval or authorization. Back office server 30 sends 541 an approvalor authorization to the determined point of sale lane. At the point ofsale lane, an approval or authorization is received 539. At the point ofsale lane, a confirmation of the payment transactions is provided 541 toa user.

In reference now to FIG. 6A, a method for processing paymenttransactions is shown. A request to process a payment is received 602. Adetermination 604 is made that the request is associated with one of aplurality of credit card terminals at a retail location. A request issent 606 to the determined credit card terminal to initiate receipt ofsecure payment information. The determined credit card terminal receives608 secure payment information. The determined credit card terminalsends 610 the secure payment information to a remotely located serverfor authorization. The determined credit card terminal receives 612 anauthorization from a remotely located server.

In some embodiments, a request to process a payment is received. Adetermination is made that the request is associated with a credit cardterminal at a retail location. A request is sent to the determinedcredit card terminal to initiate receipt of secure payment information.The determined credit card terminal received secure payment information.The determined credit card terminal sends the secure payment informationto a remotely located server for authorization. The determined creditcard terminal receives an authorization from a remotely located server.

In reference now to FIG. 6B, a method for processing paymenttransactions is shown. A request to process a payment is received 602from an electronic cash register. A determination 604 is made that therequest is associated with one of a plurality of credit card terminalsat a retail location. A request is sent 606 to the determined creditcard terminal to initiate receipt of secure payment information. A useris prompted 607 to input secure payment information at the determinedcredit card terminal. The determined credit card terminal receives 608the secure payment information. The determined credit card terminalsends 610 the secure payment information to a remotely located serverfor authorization. The determined credit card terminal receives 612 anauthorization from the remotely located server. The determined creditcard terminal sends 614 a payment authorization without PCI scopeinformation. The electronic cash register receives 616 a paymentauthorization without PCI scope information.

In reference now to FIG. 7A, a system for managing customerrelationships in the context of processing payment transactions isdepicted. Back office server 30 is in communication with customerrelationship management (CRM) server 40. Server 40 may be a singleserver, a plurality of servers, a server farm, or an allocation ofcomputing services provided by a cloud based provider of computerservices. In some embodiments, server 40 may be a plurality of serversoperated by a plurality of different parties, entities, and serviceproviders. Server 40 may also be in communication with paymentprocessing server 50. In some embodiments, communications between server30 and server 40 are encrypted. In some embodiments, communicationsbetween server 30 and server 40 are encrypted using public-private keyencryption. In some embodiments, communications between server 30 andserver 40 are encrypted using shared secret key encryption. In someembodiments, communications between server 30 and server 40 areencrypted using Secure Socket Layer (SSL) or Transport Layer Security(TLS) protocols. In some embodiments, communications between server 30and server 40 are encrypted using a proprietary encryption scheme. Insome embodiments, communications between server 30 and server 40 mayoccur, at least in part, wirelessly.

In some embodiments, communications between back office server 30 andCRM server 40 may occur through one or both of firewalls 60 and 65.Communication between server 30 and server 40 may occur across thepublic Internet. In some embodiments, communications between server 30and server 40 occur across a virtual private network (VPN). In someembodiments, communication between server 30 and server 40 occur acrossany form of wide area network. In some embodiments, communicationsbetween server 30 and server 40 occur across a private network. In someembodiments, communications between server 30 and server 40 may occur,at least in part, wirelessly.

In reference now to FIG. 7B, a system for managing customerrelationships in the context of processing payment transactions isdepicted. A CRM server 40 is comprised of a loyalty program manager 42and a receipts manager 44. The loyalty program manager 42 may be anycomputing processor or portion thereof programmed to perform thefunctions of a loyalty program manager. The receipts manager 44 may beany computing processor or portion thereof programmed to perform thefunctions of a receipts manager. In some embodiments the loyalty programmanager 42 and receipts manager 44 may comprise a single joint loyaltyprogram and receipts manager. In some embodiments, the functions of theloyalty program manager may be performed by the receipts manager 44. Insome embodiments, the loyalty program manager 42 may perform thefunctions of the receipts manager. CRM server 40 may be in communicationwith storage 50. In some embodiments, storage 50 may be in the form of adatabase. In some embodiments, loyalty program manager 42 and/orreceipts manager 44 are in communication with payment processing service51. In some embodiments, loyalty program manager 42 and/or receiptsmanager 44 are in communication with back office manager 32.

In reference now to FIG. 8, a method for managing customer relationshipsin the context of processing payment transactions is depicted. Adetermination 802 is made, based at least in part on paymentinformation, that a customer belongs to a loyalty program. Loyaltyprogram information is applied 804 to the requested transaction.Transaction information is stored 806 with other loyalty programinformation. Loyalty program information is sent 808 to a retaillocation. A determination 810 is made as to which point of sale laneloyalty program information applies. Loyalty program information is sent812 to the determined point of sale lane.

In reference now to FIG. 9, a method for managing customer relationshipsin the context of processing payment transactions is depicted. A tokenfor a customer is determined 902, based at least in part on paymentinformation. A determination 904 is made, based at least in part on saidtoken, as to whether a customer belongs to a loyalty program.Transaction information is stored 906 with an association to said token.Said token is received 908 at a retail location. Loyalty programinformation is applied 910 to a transaction based, at least in part, onsaid token. A token may be any computer readable identifier for acustomer, including a data packet, address in memory, message, file,hash, or database entry.

What is claimed is:
 1. A method for processing a payment transaction atretail locations, the method comprising: initiating, by a computingdevice at a retail location, a payment transaction; receiving, by acomputing device at a retail location, non-PCI scope information in theform of a unique identifier via a mobile device; determining, by aremotely located payment processing server, that the payment transactionis authorized based at least in part on said non-PCI scope information;receiving, by the computing device at the point of sale, anauthorization for the payment transaction from the remotely locatedpayment processing server; wherein the payment transaction is processedwithout relying on PCI-scope information at the retail location.
 2. Themethod of claim 1, further comprising: determining, at the retaillocation, that the authorization for the payment transaction isassociated with a particular point of sale lane of a plurality of pointof sale lanes at the retail location.
 3. The method of claim 2, furthercomprising: sending the authorization to the particular point of salelane associated with the payment transaction.
 4. The method of claim 1,wherein said non-PCI scope information in the form of a uniqueidentifier is associated with a customer loyalty program.
 5. The methodof claim 4, further comprising: applying customer loyalty programinformation to the payment transaction based, at least in part, on saidnon-PCI scope information in the form of a unique identifier.
 6. Acomputing device for processing payments at retail locations, thecomputing device comprising: at least one processor; and a memorycommunicatively coupled to the at least one processor and storingcomputer-executable instructions, the computer-executable instructions,when executed by the at least one processor, cause the securedelectronic device to: initiate a payment transaction; receive non-PCIscope information in the form of a unique identifier from a mobiledevice; receive an authorization for the payment transaction from aremotely located payment processing server, wherein said authorizationwas determined by said remotely located payment processing server based,at least in part, on said non-PCI scope information; and wherein thepayment transaction is processed without relying on PCI-scopeinformation at the retail location.
 7. The computing device of claim 6,wherein the authorization for the payment transaction is associated witha particular point of sale lane of a plurality of point of sale lanes atthe retail location.
 8. The computing device of claim 7, wherein theauthorization is sent to the particular point of sale lane associatedwith the payment transaction.
 9. The computing device of claim 7,wherein said non-PCI scope information in the form of a uniqueidentifier is associated with a customer loyalty program.
 10. The methodof claim 9, wherein customer loyalty program information is applied tothe payment transaction based, at least in part, on said non-PCI scopeinformation in the form of a unique identifier.
 11. A non-transitorycomputer-readable storage medium with computer readable instructionsstored thereon, the computer readable instructions, when executed by acomputing device, cause the computing device to perform a method forprocessing a payment transaction, the method comprising: initiating, bya computing device at a retail location, a payment transaction;receiving, by a computing device at a retail location, non-PCI scopeinformation in the form of a unique identifier via a mobile device;determining, by a remotely located payment processing server, that thepayment transaction is authorized based at least in part on said non-PCIscope information; receiving, by the computing device at the point ofsale, an authorization for the payment transaction from the remotelylocated payment processing server; wherein the payment transaction isprocessed without relying on PCI-scope information at the retaillocation.
 12. The non-transitory computer-readable storage medium ofclaim 11, wherein the computer readable instructions, when executed bythe computing device, further cause the computing device to perform amethod further comprising: determining, at the retail location, that theauthorization for the payment transaction is associated with aparticular point of sale lane of a plurality of point of sale lanes atthe retail location.
 13. The non-transitory computer-readable storagemedium of claim 12, wherein the computer readable instructions, whenexecuted by the computing device, further cause the computing device toperform a method further comprising: sending the authorization to theparticular point of sale lane associated with the payment transaction.14. The non-transitory computer-readable storage medium of claim 11,wherein said non-PCI scope information in the form of a uniqueidentifier is associated with a customer loyalty program.
 15. Thenon-transitory computer-readable storage medium of claim 11, wherein thecomputer readable instructions, when executed by the computing device,further cause the computing device to perform a method furthercomprising: applying customer loyalty program information to the paymenttransaction based, at least in part, on said non-PCI scope informationin the form of a unique identifier.